home *** CD-ROM | disk | FTP | other *** search
- This message announces the availability of patch level 2 of version
- 0.08 of Linux/68k.
-
- It can be ftped from directory /pub/linux/680x0 at tsx-11.mit.edu.
-
- A precompiled kernel executable can be found in vmlinux-0.08pl2.gz in
- the "kernel" subdirectory. The "bootstrap" program from 0.08 should
- be used to boot the new kernel.
-
- The patch for the kernel source can be found in linux-0.08pl2.diffs.gz
- in the "src" subdirectory.
-
- The changes in this release against 0.08 patch level 1:
-
- *) Major changes to the low level Amiga console code contributed by
- William Rucklidge <wjr@cs.cornell.edu>. These changes add AGA modes
- to the console driver. See below.
-
- *) With the help of William Rucklidge <wjr@cs.cornell.edu>, we should
- have the '040 cache problems cleared up now.
-
- *) Addition of the SEAGATE ST177N drive to the SCSI "blacklist" of
- drives which shouldn't be probed at LUN != 0.
-
- *) High level terminal emulation bug fixes from Dave Carter
- (carter@compsci.bristol.ac.uk).
-
- *) Misc. small cleanups.
-
- This release still contains only support for the Amiga.
-
- I've recently received source code changes for rudimentary Atari
- support. These will be incorporated into the main Linux/68k sources
- as soon as possible.
-
- To boot the kernel on an Amiga, use the supplied "bootstrap" command.
-
- The video mode can now be selected on the bootstrap command line.
- The video option is given using "video=mode[,inverse]", where the
- allowed modes are:
- ntsc -> put the console in a non-interlaced NTSC mode (80x25)
- ntsc-lace -> put the console in an interlaced NTSC mode (80x50)
- pal -> put the console in a non-interlaced PAL mode (80x32)
- pal-lace -> put the console in an interlaced PAL mode (80x64)
- aga640x480 -> put the console in a 31Khz VGA compatible mode (80x60)
- aga800x600 -> put the console in an 800x600 Super72 compatible
- interlaced mode (112x78)
-
- If you specify the optional "inverse" keyword, the console will use
- reverse video (white on black).
-
- For example, to boot with an inverse non-interlaced pal screen, you
- would boot with the parameter "video=inverse,pal". To boot with an
- interlaced ntsc screen, you would boot with the parameter
- "video=ntsc-lace".
-
- If you do not specify a video mode on the bootstrap command line, the
- console code picks an "appropriate" mode based on available
- information.
-
- It chooses the "aga640x480" machine on machines with the AGA chipset.
- Otherwise, It chooses a PAL mode on PAL machines and NTSC otherwise.
- It chooses interlaced on A3000 machines and non-interlaced otherwise.
-
- ***NOTE*** Now that the console code changes scan rates, be very sure
- that the mode you boot in is the appropriate one for your monitor.
-
- ***NOTE*** also that neither the NTSC or PAL modes (OCS modes) mess
- around with any of the ECS programmable scan rate registers, so if you
- have ECS, your video hardware must be already set to the appropriate
- scan rate before you boot Linux.
-
- Please note that to boot with the new image, you must place the new
- "vmlinux" file in the AmigaDOS directory from which you invoke the
- "bootstrap" program. The "/vmlinux" symbolic link in the
- "root.tar.gz" file is just there as a convenience for looking up
- kernel symbols. This symbolic link has nothing to do with booting.
-
- To boot with the ram disk image, uncompress the image and type:
-
- bootstrap -r new-filesys ro
-
- The "ro" option tells the kernel to mount the ramdisk as read-only.
- The "/etc/rc" file on the ramdisk image will "check" the ramdisk image
- and re-mount the root (ram disk) file system read/write. The ram disk
- image contains an "/sbin/shutdown" script which will unmount all
- file systems, mount the ram disk read-only, sync all dirty buffers, and
- then print a message indicating that it is safe to reboot.
-
- You can boot from an existing Linux hard disk partition by supplying
- the device name to the bootstrap program:
-
- bootstrap root=/dev/[sh]d[a-f][1-16]
-
- You probably want to provide the "ro" option to initially mount the
- partition read-only.
-
- The major number for SCSI disks is "0x08", and the minor number
- depends on the disk and partition. linux/68k searches for SCSI disks
- from target 0 to target 7, and for Logical Units 0 through 7 on each
- target. The minor number can be calculated by (disk_number)*16 +
- partition_number. The first disk found is disk 0. Partition 0 is the
- whole disk. Partition 1 is the first partition found in the
- RigidDiskBlock partition table on the Amiga hard disk. Thus 0x0801 is
- the first partition on the first disk found. 0x0812 is the second
- partition on the second hard disk found.
-
- For example, I have two SCSI hard disks. The first is at target 5,
- LUN 0 and the second at target 6, LUN 0. The first has three
- partitions (used for Linux) and the second has 4 partitions used for
- AmigaDOS.
-
- Thus I have:
-
- devnum linux device name
- ------ ------------------------------------
- 0x0800 sda (the entire disk at target 5 : BE CAREFUL)
- 0x0801 sda1 (1st partition on disk at target 5)
- 0x0802 sda2 (2nd partition on disk at target 5)
- 0x0803 sda3 (3rd partition on disk at target 5)
- 0x0810 sdb (the entire disk at target 6 : BE CAREFUL)
- 0x0811 sdb1 (1st partition on disk at target 6)
- 0x0812 sdb2 (2nd partition on disk at target 6)
- 0x0813 sdb3 (3rd partition on disk at target 6)
- 0x0814 sdb4 (4th partition on disk at target 6)
-
- *NOTE* The target numbers above are examples; these are what I get on
- my system, since the first disk is at target 5 and the second at
- target 6. If your first disk is at target 0, your sda will *still* be
- 0x0800 (/dev/sda).
-
- My Linux root partition is on the 1st partition of my first drive, so
- I boot with:
-
- bootstrap root=/dev/sda1
-
- After booting from one of the above methods, if the kernel supports
- your SCSI driver, you should be able to create a minix file system on
- one of your hard disk partitions if you wish.
-
- Determine the size of your partition in 1K blocks (take the number of
- 512 byte sectors from HDToolBox and divide by two), and determine
- which special file to use in /dev (see above). *DOUBLE CHECK* that
- the major/minor numbers for the special device (ls -l /dev/xxx) are
- correct. If they are incorrect or the device special file doesn't
- exist, use mknod to change or create the device special file. Then
- execute:
-
- /sbin/mkfs.minix /dev/xxxx size
-
- This will create a minix file system on the hard disk partition. You
- can then mount this partition under /mnt and copy files to it:
-
- mount /dev/xxxx /mnt
-
- When finished copying, unmount the partition:
-
- umount /mnt
-
- sync a few times, run "/sbin/shutdown" and then reboot. You can then
- boot the kernel by providing "bootstrap" with the device name to boot
- from.
-
- Again, you do any mucking around with hard disks at your OWN RISK.
-
- Note that the above can be used on IDE hard disks now also, except
- that the major/minor numbers for IDE hard disks are different, and the
- special devices in /dev are named hd[ab][1-64].
-